home *** CD-ROM | disk | FTP | other *** search
- From: mforget@elfhaven.ersys.edmonton.ab.ca (Michel Forget)
- Subject: Re: Gem List (fwd)
- Date: Tue, 19 Jul 1994 21:57:36 -0600
- Precedence: bulk
-
- Hello Chris,
-
- >And when are you releasing the source code?
-
- Every time I've mentioned this, there has been no response. I have a
- feeling it will not be released. That is his right, of course, but
- I'd like to see the demonstration program he keeps talking about.
-
- >Something that just occured to me, folks... WHY are we discussing various
- >GEM libraries on the gem-list at this point? I thought we were trying
- >to hammer out some standards here... I'm amazed at how argumentative this
- >mailing list is (but then, I guess *all* Atari users need to blow off
- >steam somehow these days).
-
- I'm not actually sure; I can only speak for myself, but I tend to respond
- when people say something I disagree with. That is why I keep posting
- these messages, though.
-
- >Reasonable C support libraries should have malloc() and free() in them
- >that keep track of larger chunks (usually 64k from what I've seen); that
- >way, if you're going to malloc() a bunch of small things, and free() a
- >few, then malloc() a few more, you're not fragmenting memory... I'm
- >presuming that you're playing devil's advocacte a little here, since nobody
- >in their right mind would use the Malloc() GEMDOS call.
-
- Sigh. _I_ use it. (Yes, I feel stupid now, since now at least one reason
- why I should not.) Using malloc() is only a delay, though, for TOS 1.0
- users. If you allocate a lot of memory (like MasterBrowse does) then
- malloc() will end up calling Malloc() more that sixteen times, and you
- can say bye-bye to TOS 1.0. Is there -another- reason why I should not
- use it?
-
-
- --
- Michel Forget \\ mforget@elfhaven.ersys.edmonton.ab.ca //
- Electric Storm Software \\ ess@tibalt.supernet.ab.ca //
- PGP Public Key Finger. = 1F C0 D3 FE 40 51 7F 47 F3 4A C6 AD 6E 02 71 85
-